Skip to content

Add info for debugging high CPU utilization#191

Draft
gtjoseph wants to merge 1 commit intoasterisk:mainfrom
gtjoseph:main-cpu-troubleshooting
Draft

Add info for debugging high CPU utilization#191
gtjoseph wants to merge 1 commit intoasterisk:mainfrom
gtjoseph:main-cpu-troubleshooting

Conversation

@gtjoseph
Copy link
Copy Markdown
Member

No description provided.

@gtjoseph gtjoseph marked this pull request as draft April 20, 2026 16:01
@gtjoseph
Copy link
Copy Markdown
Member Author

It's a start. What else should be covered?

Comment thread docs/Deployment/Troubleshooting/Troubleshooting-High-CPU-Utilization.md Outdated
Comment thread docs/Deployment/Troubleshooting/Troubleshooting-High-CPU-Utilization.md Outdated
@gtjoseph gtjoseph force-pushed the main-cpu-troubleshooting branch from 5c8ad86 to 269e09e Compare April 21, 2026 14:46
@gtjoseph gtjoseph requested a review from mbradeen April 21, 2026 14:46
with the _what_ first because it might not even be Asterisk itself. The tool of choice
here is the venerable `top` or it's relatives `htop` and `btop`.

So who are the culprits?
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So who are the most common culprits?


#### Still can't figure it out?

If Asterisk is still using more CPU than you think is necessary, it's time to ask for help.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before doing this I'd add a paragraph about reducing the environment (their specific usage) to specific parts which can be disabled and using that to identify the aspects that are contributing to high CPU usage, and consequences, in their environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants